@FWuellhorst : I don't think the two events close to each other will pose an issue. I suggest we keep the counter always present as it is now.
I also cleaned up the model to remove two instance of ySetOn which were equal and removed the size of the boundary check blocks as they were overlapping with a not block underneath.
From my point of view this is ready to be merged.

A future improvement could be to put yOn after the on off safety control on the bus, and then use this in the downstream blocks to avoid the multiple instances of ySetOn.

Thanks for the adjustments. I further added revisions.

Regarding yOn, this will not work with the current serial control logic, where one output affects the others. While series connection is required for the onOff checks, the other three blocks could be put in parallel, if I am not mistaken. Still, one global yOn would not work.

The idea is to put the downstream safety blocks in parallel, and they all get the on signal as computed after the first block, or its bypass if the block is conditionally removed.